se.cs.ieu.edu.tr
Course Name | |
Code | Semester | Theory (hour/week) | Application/Lab (hour/week) | Local Credits | ECTS |
---|---|---|---|---|---|
Fall/Spring |
Prerequisites | None | |||||
Course Language | ||||||
Course Type | Elective | |||||
Course Level | - | |||||
Mode of Delivery | - | |||||
Teaching Methods and Techniques of the Course | Application: Experiment / Laboratory / Workshop | |||||
Course Coordinator | - | |||||
Course Lecturer(s) | - | |||||
Assistant(s) | - |
Course Objectives | |
Learning Outcomes | The students who succeeded in this course;
|
Course Description |
| Core Courses | |
Major Area Courses | ||
Supportive Courses | ||
Media and Managment Skills Courses | ||
Transferable Skill Courses |
Week | Subjects | Required Materials |
1 | Introduction, basic terms & concepts in information security & related legal issues | Preliminary study 1 |
2 | Basics of OS Security; concepts, general & common problems, threats, countermeasures | Preliminary study 2 |
3 | Access controls & methodologies, IAAA in OS & relevant technologies & applications in today’s world | Preliminary study 3 |
4 | Centralized / decentralized IAAA solutions, different IAAA architectures in secure OS | Preliminary study 4 |
5 | Audit & monitoring in OS | Preliminary study 5 |
6 | Intro to cryptography, protection of assets, data, systems in OS with today’s best practices | Preliminary study 6 |
7 | Secure system management; models, solutions, various technologies | Preliminary study 7 |
8 | Midterm | |
9 | Opensource architecture & approach and its relation with information security & OS security | Preliminary study 8 |
10 | IAAA differences of Linux vs. Windows architectures | Part I Guide to Operating Systems Security, Michael Palmer |
11 | IAAA differences of Linux vs. Windows architectures | Part II Guide to Operating Systems Security, Michael Palmer |
12 | Network related issues in OS Security | Part I Guide to Operating Systems Security, Michael Palmer |
13 | Network related issues in OS Security (including cryptographic basics) | Part II Guide to Operating Systems Security, Michael Palmer |
14 | Related vulnerabilities, threats & countermeasures (DOS attacks, malicious codes, XSS, rootkits, JavaScript, SQL, Ajax, .Net, Apache, IIS, etc) | Part I Guide to Operating Systems Security, Michael Palmer |
15 | Related vulnerabilities, threats & countermeasures (DOS attacks, malicious codes, XSS, rootkits, JavaScript, SQL, Ajax, .Net, Apache, IIS, etc) | Part II Guide to Operating Systems Security, Michael Palmer |
16 | Review of the Semester |
Course Notes/Textbooks | Guide to Operating Systems Security, Michael Palmer, Publisher: Thomson, 2003 (2004 2nd ed), ISBN 13: 9780619160401©2004, ISBN 10: 0619160403 |
Suggested Readings/Materials | Maximum Linux Security (2nd Edition), John Ray, Sams, 2 Pap/Cdr edition, 2001, ISBN10: 0672321343, ISBN13: 9780672321344 Hacking Exposed Windows Server 2003, Joel Scambray & Stuart McClure, McGrawHill Osborne Media, 2006, ISBN10: 0072230614, ISBN13: 9780072230611 CISSP Textbook, Vallabhaneni, S.Rao, SRV Pro Publications, 2002, ASIN: B0006S7QN0 ISO27001:IEC, British Standards Institution, 2005 Hacking Exposed: Network Security Secrets & Solutions, Stuart McClure, et al, McGrawHill Osborne, Fourth Edition, 2003, ISBN 0072227427 Applied Cryptography: Protocols, Algorithms, and Source Code in C, Schneier, Bruce, Second Edition, 1998, ISBN 0471117099 Hacking Exposed Web Applications, Scambray, Joel, et al, Second Edition, McGrawHill Osborne, 2006, ISBN 0072262990 |
Semester Activities | Number | Weigthing |
Participation | ||
Laboratory / Application | 5 | 10 |
Field Work | ||
Quizzes / Studio Critiques | ||
Portfolio | ||
Homework / Assignments | 4 | 40 |
Presentation / Jury | ||
Project | ||
Seminar / Workshop | ||
Oral Exam | ||
Midterm | 1 | 20 |
Final Exam | 1 | 30 |
Total |
Weighting of Semester Activities on the Final Grade | 70 | |
Weighting of End-of-Semester Activities on the Final Grade | 30 | |
Total |
Semester Activities | Number | Duration (Hours) | Workload |
---|---|---|---|
Course Hours (Including exam week: 16 x total hours) | 16 | 2 | 32 |
Laboratory / Application Hours (Including exam week: 16 x total hours) | 16 | 2 | |
Study Hours Out of Class | 6 | 2 | |
Field Work | |||
Quizzes / Studio Critiques | |||
Portfolio | |||
Homework / Assignments | 4 | 5 | |
Presentation / Jury | |||
Project | |||
Seminar / Workshop | |||
Oral Exam | |||
Midterms | 1 | 10 | |
Final Exams | 1 | 36 | |
Total | 142 |
# | Program Competencies/Outcomes | * Contribution Level | ||||
1 | 2 | 3 | 4 | 5 | ||
1 | Be able to define problems in real life by identifying functional and nonfunctional requirements that the software is to execute | |||||
2 | Be able to design and analyze software at component, subsystem, and software architecture level | |||||
3 | Be able to develop software by coding, verifying, doing unit testing and debugging | X | ||||
4 | Be able to verify software by testing its behaviour, execution conditions, and expected results | |||||
5 | Be able to maintain software due to working environment changes, new user demands and the emergence of software errors that occur during operation | |||||
6 | Be able to monitor and control changes in the software, the integration of software with other software systems, and plan to release software versions systematically | |||||
7 | To have knowledge in the area of software requirements understanding, process planning, output specification, resource planning, risk management and quality planning | |||||
8 | Be able to identify, evaluate, measure and manage changes in software development by applying software engineering processes | |||||
9 | Be able to use various tools and methods to do the software requirements, design, development, testing and maintenance | X | ||||
10 | To have knowledge of basic quality metrics, software life cycle processes, software quality, quality model characteristics, and be able to use them to develop, verify and test software | |||||
11 | To have knowledge in other disciplines that have common boundaries with software engineering such as computer engineering, management, mathematics, project management, quality management, software ergonomics and systems engineering | X | ||||
12 | Be able to grasp software engineering culture and concept of ethics, and have the basic information of applying them in the software engineering | X | ||||
13 | Be able to use a foreign language to follow related field publications and communicate with colleagues | X |
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest